home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Libris Britannia 4
/
science library(b).zip
/
science library(b)
/
COMMUNIC
/
0896.ZIP
/
RCOMM.DOC
< prev
next >
Wrap
Text File
|
1988-01-22
|
26KB
|
568 lines
RCOMM - Resident Communications. Version 2.0 Page 1
Copyright (C) 1988 by Thomas Duller. All rights reserved.
Let's get the legal stuff over with right away.
RCOMM is provided on an "as is" basis without warranty of any
kind express or implied. In no event will Thomas Duller
(hereafter referred to as the Author), be liable to you for any
damages, including any lost profits, lost savings or other
incidental or consequential damages arising out of the use of or
inability to use RCOMM, even if the Author has been advised of
the possibility of such damages, or for any claim by any other
party.
RCOMM is copyrighted by the Author. You are encouraged to give
copies to your friends and upload it to bulletin boards, however
sale of RCOMM for profit by anyone except the Author is strictly
prohibited.
If you use this program and find it to be of value, your
contribution would be greatly appreciated. I have put together
a formula to determine the contribution amount.
First, set a figure how much you think your time is worth per hour.
Second, keep track of how much time you save (or gain) by using
RCOMM for two weeks.
Third, multiply your $ per hour by the number of hours saved and
send me a check for that amount. The rest of your life is free of
charge!
If that sounds too much like work, just send me $25.00. (a steal)
I'd like that a lot.
Send contributions to:
Thomas Duller
P.O. Box 27095
Milwaukee, WI. 53227
and if you think of it, let me know where you received RCOMM and
what you would like to see in future releases.
Contributors will receive notification when new releases become
available. The Author reserves the right to charge a reasonable
amount (probably around $5.00) to cover postage, handling etc.
for distrubution.
Site licenses and/or customized versions may be available. Send
me a letter detailing your requirements and we can probably work
something out.
RCOMM - Resident Communications. Version 2.0 Page 2
Copyright (C) 1988 by Thomas Duller. All rights reserved.
Ok, so what is RCOMM and why should you use it? Glad you asked.
Chances are that you downloaded this file from a BBS since that's
my primary distribution channel. Let me ask you a question. What
were you doing while you were downloading it?
If you are like most people, you sat there watching a bunch of
meaningless numbers flash on the screen. Don't you have better
things to do with your time? Like balance your checkbook, or
write a letter to your Mom, or update your resume? Well with
RCOMM you can do both at the same time! That's right, RCOMM will
handle all of your file transfers in the background while you do
better things with your valuable time.
Features include:
* Memory resident upload and download with XMODEM, YMODEM and
variations of those protocols including autodownload.
* Pop-up terminal mode.
* PC-TALK compatible dialing directory.
* File transfer monitor mode.
* Terminal capture mode.
* Easy installation
* Not copy protected
* Not "crippleware". What you've got is what there is.
* Shareware. Try it out before you pay for it.
* Can be used in conjunction with your current comm program.
RCOMM - Resident Communications. Version 2.0 Page 3
Copyright (C) 1988 by Thomas Duller. All rights reserved.
System requirements:
IBM XT, AT or true compatible.
DOS 2.0 or higher.
Two floppy drives or preferably a hard disk.
A Hayes (or compatible) modem.
note - carrier detect should *not* be forced high. On
hayes modems you want switch 6 in the up position.
CONFIG.SYS file on boot disk should contain extra FILES and
BUFFERS. 25 of each is suggested. Consult your DOS manual on
how to set up your own CONFIG.SYS file.
Installation:
The first thing you should do is make a backup copy of the
original RCOMM disk. It's not copy protected, so you can use
diskcopy or just do a copy *.*.
Hard disk installation:
There is an install batch file you can run and RCOMM will install
itself. It is named "INSTALLH.BAT" and it can run from either a
floppy or a hard disk subdirectory. Just set the current
directory to where the files are and enter "INSTALLH". If you
use the install batch file it will do the following:
1. Create a directory called C:\RCOMM and install itself into
it.
2. Create a directory called C:\DOWNLOAD where batch and auto-
downloaded files will go.
When the install is completed check your config.sys file and make
sure you have the "files" and "buffers" commands in it. If you
don't, RCOMM will probably still work ok but other programs may
find themselves unable to open files.
The following screen dump illustrates the defaults set up by the
install. If you want to change any of them, run RCONFIG.COM.
_________________________________________________________________
Baud rate : 1200
Parity : none
Data bits : 8
Comm port : COM1
Modem type : Hayes
Sound : off
Batch file transfer drive : C:
Batch file transfer path : \DOWNLOAD
Modem dialing prefix : ATDT
Modem init string : ATL1 Q1
Dialing directory pathname : C:\RCOMM\PC-TALK.DIR
Dialing directory type : PC-Talk Compatible
________________________________________________________________
RCOMM - Resident Communications. Version 2.0 Page 4
Copyright (C) 1988 by Thomas Duller. All rights reserved.
If you're like me and don't trust install files you can install
RCOMM manually following these steps:
First I'll assume that the original files are on drive a:. If
they are somewhere else, adjust accordingly.
1. Create a directory where you want the programs to go.
2. copy a:*.com to that directory.
3. copy a:*.exe to that directory.
4. copy a:rcomm.dah as rcomm.dat to that directory.
5. copy a:pc-talk.dir to that directory.
6. Copy the .doc files too, if you wish.
7. Check your \config.sys file. Make sure you have the
following entries: FILES=25 and BUFFERS=25.
8. Run RCONFIG.COM and get everything set up the way you
want it.
RCOMM - Resident Communications. Version 2.0 Page 5
Copyright (C) 1988 by Thomas Duller. All rights reserved.
Floppy disk installation:
There is an install batch file you can run and RCOMM will install
itself. It is named "INSTALLF.BAT". Just set the current
drive to where the files are, put a blank, bootable floppy in
drive b: and enter "INSTALLF". This is a copy of the batch file
so you can see what it does.
b:
copy a:rcomm.com
copy a:rconfig.com
copy a:rmaint.exe
copy a:rcomm.daf rcomm.dat
copy a:pc-talk.dir
copy a:rcomm.doc
The following screen dump illustrates the defaults set up by the
install. If you want to change any of them, run RCONFIG.COM.
________________________________________________________________
Baud rate : 1200
Parity : none
Data bits : 8
Comm port : COM1
Modem type : Hayes
Sound : off
Batch file transfer drive : B:
Batch file transfer path :
Modem dialing prefix : ATDT
Modem init string : ATL1 Q1
Dialing directory pathname : A:PC-TALK.DIR
Dialing directory type : PC-Talk Compatible
________________________________________________________________
Note: on two floppy systems I highly recommend using a RAM
disk for downloading, otherwise you are liable to forget and
change floppies while downloading. The results of changing
floppies while downloading are unpredictable, but I promise, it
won't be nice.
RCOMM - Resident Communications. Version 2.0 Page 6
Copyright (C) 1988 by Thomas Duller. All rights reserved.
OK, now it's installed.
You might want to run RMAINT.EXE now to check out the dialing
directory. I have included one with the phone number of my
favorite BBS. If you have your own PC-TALK.DIR, you can copy it
over this one. Otherwise run RMAINT.EXE and poke your phone
numbers etc. in. I admit it's not the prettiest program I ever
wrote, but it's self explanatory and you don't have to run it
very often anyway.
The next thing to look at is the RCOMM configuration file. If
you used the install batch and have a 1200 baud (or better) modem
on COM1:, you are ready to go. If you need to change anything,
run RCONFIG.COM. I won't go into a lot of boring detail about it
here. Each screen has it's own help and hints and if you use the
default configuration files as a starting point you'll have no
problems with it.
RCOMM - Resident Communications. Version 2.0 Page 7
Copyright (C) 1988 by Thomas Duller. All rights reserved.
Having read and followed the directions so far, you are now ready
to run RCOMM. I assume you have the current drive or path set to
where the RCOMM files are, so just enter RCOMM.
You will be treated to another disclaimer and plea for money
and then you will see the contents of the configuration file.
(A quick aside here. If you want to put RCOMM in your
autoexec.bat file, you can get by these two screens by piping in
a file containing two space characters :
RCOMM <spsp.txt).
So anyway, you see those two screens and then...huh?...I got a
C> prompt back. Yes that's the way RCOMM works. If you want to
use it now, hold the *right* shift and control keys simultaneously.
This key combination will cause RCOMM to activate. Whatever is
currently running will be saved and RCOMM will take over. Don't
worry, when you exit RCOMM, you will be right back where you left
off.
If you don't know what to do next, you can press the <home> key
and get a function key summary. I will detail the function keys
here in alphabetical order.
<Alt-C> - Clears the screen. If up/downloading the transfer
status information will be refreshed.
<Alt-D> - Dialing directory.
You can either select an entry from the directory or
manually enter a number.
If you select from the directory, the com port will be
set up using the information from the directory entry.
If you want to enter a number by hand you will first
go through a screen which looks suspiciously like one
of the RCONFIG screens to enter the com port setup.
If it all looks ok, just bang on the return key until
you get out, otherwise you can change any of the fields
displayed.
When dialing, you will always be asked if you want call
waiting disabled. If you say yes, a "1170," will be
added to the front of the dial string. This seems to
be the standard way of disabling call waiting.
<Alt-H> - Hangs up the phone. Now. No questions asked.
<Alt-K> - Toggle for terminal "kapture" mode.
If kapture is currently off, you will be prompted for
a file name. If the name you enter already exists, the
old file will be overwritten. A <kap> indicator will
appear on the status line whenever kapture is in use.
If kapture is currently on, hitting <Alt-K> will close
the kapture file and stop kapturing.
RCOMM - Resident Communications. Version 2.0 Page 8
Copyright (C) 1988 by Thomas Duller. All rights reserved.
In addition, the kapture file will be closed whenever
you start an up/download automatically.
For the time being, kapturing can only be done in the
foreground. One of these days, I'll allow it in the
background as well.
<Alt-M> - File transfer monitor mode.
This also acts as an on/off toggle. When a file
transfer is in progress, you can watch the characters
go by. It usually looks like garbage. Actually this is
just some test code I left in because for some reason
people thought is was neat to watch. I don't know....
<Alt-P> - Change com port setup.
Use this to set baud rate, etc. when you don't use the
directory for dialing.
<Alt-Q> - Quick dial phone.
This is the same as using <Alt-D> to dial from the
directory except that the directory display is bypassed
and you just get a prompt for what entry to dial. Use
this if you know what entry you want to dial already.
<Alt-R> - Receive (download) a file.
You will first be asked what protocol to use. Available
protocols include:
Xmodem, Xmodem CRC, Ymodem (single and batch), Ymodem-G
(single and batch).
For Xmodem and single file Ymodem, you will be asked
for a file name.
ENTER THE FULL PATH NAME!!!!! Include drive, path and
filename. If you just enter a file name and then change
to another directory, half of your file will end up in
the wrong directory if you are lucky. If you are not
the lucky type, your PC will probably lock up real tight.
For the batch protocols and autodownload, the file name
from the sender will be combined with the download path
from the RCOMM config file to make up the full path
name.
<Alt-T> - Transmit (upload) a file.
You will first be asked what protocol to use. Available
protocols include:
Xmodem, Xmodem CRC, Ymodem (single and batch), Ymodem-G
(single and batch).
You will then be asked for a file name. See above for
the importance of entering the full path name. If you
use one of the Ymodem batch protocols, you may enter
wildcards in the filename.
RCOMM - Resident Communications. Version 2.0 Page 9
Copyright (C) 1988 by Thomas Duller. All rights reserved.
<Alt-X> - Returns you to whatever you were doing when you popped
RCOMM in. If you are up/downloading, it will continue
in the background. You may pop back up at any time to
check on it if you wish. If you are dialing it will
continue to dial in the background. When you get a
connect, RCOMM will start beeping. You may then pop
RCOMM up using the <right shift>/<cntl> combination
and begin your terminal session.
That wraps up the function keys. As you can see it's a fairly
simple straightforward program. It has to be. Nobody wants a
200k TSR sitting around.
General information:
RCOMM hooks the following interrupt vectors:
08h - timer
21h - DOS function
28h - DOS idle
63h - General, user defined.
RCOMM is a "well behaved" TSR. This means that it never does
anything that is not safe and put things back the way they were
when it gets done (in layman's terms).
RCOMM - Resident Communications. Version 2.0 Page 10
Copyright (C) 1988 by Thomas Duller. All rights reserved.
New features/bug fixes.
- Ymodem-G is now reliable enough to be among the supported
protocols.
- A monitor function has been added. If you want to, you can
watch the characters being sent/received while a file transfer
is in progress. Binary files look like garbage, but it's there
if you want it.
- Terminal session capture has been added.
- A status line has been added to the bottom of the terminal
screen. It displays the date, time and status of the capture
and monitor toggles.
- Most screens have been re-designed to make them, hopefully,
more user friendly.
- The RCONFIG program has been re-written and is now nearly
comprehensible.
- There were times when RCOMM would appear to lock up. As it
turns out it was usually just waiting for something to happen
with interrupts disabled. Most notably while waiting for the
first block of a download. I have enabled the keyboard whenever
it is safe to do so. There may still be times (although it
hasn't happened to me in a while now) where it may appear to
lock up. If it does, give it a few seconds before issuing a
"three fingered salute". If a character is lost while popping
up (as sometimes happens) RCOMM will time out in ten seconds
and nak the sender. This should get you going again. RCOMM
makes every effort to stay in control as long as it does not
interfere with any other programs that may be running. It has
occasionally been known to drop dead, especially when Framework
is running in the foreground. The machine keeps running and
Framework is OK, but RCOMM won't pop up anymore. I have spent
many hours trying to figure out why and finally decided not
to run Framework while on-line. I suggest you avoid it too.
- There was a bug reported that was connected with CED and several
other DOS shell type programs. RCOMM would pop up ok, but as
soon as you popped back out (sometimes before) the machine
would lock up. It turned out to be a conflict over the DOS
critical keyboard stack, so I rewrote all of my keyboard
handling routines to stay out of the way.
- There were reports of problems with dialing. I never had any
problems with my Hayes at work, so I pretty much ignored them.
When I purchased a "not quite hayes compatible" for home, I
found out what all of the griping was about. The dialing
routines are now infinitely more reliable.
RCOMM - Resident Communications. Version 2.0 Page 11
Copyright (C) 1988 by Thomas Duller. All rights reserved.
- As a side effect of my new modem I dropped the old Autocat
dialing routines. If you have one (doubtful) let me know. I
have a standalone dialing program for it.
- Just as this release was completed, another bug was reported
just in time! If you hit the <escape> key in terminal mode,
the whole machine would lock up. This was caused by the code
which supports autodownload. When an escape is received, RCOMM
goes off to look at the characters which follow it. It's usually
some handshaking before starting a download. When you hit
escape and it was echoed back to the terminal, RCOMM would go
off looking for the rest of the command and never come back!
It was a quick fix and I'm surprised that nobody else (myself
included) noticed it before. Thanks to Bruce Wilson of Des
Moines, Iowa for reporting it.
- I also rewrote the documentation from scratch. The release 1
.doc file was really bad. I think this one is only pretty
bad. Oh well, documentation was never my strong suit.
RCOMM - Resident Communications. Version 2.0 Page 12
Copyright (C) 1988 by Thomas Duller. All rights reserved.
What if.......
Everybody runs into problems now and then. That's the way
computers are. The IBM PC was not designed to run more than
one task at a time. Once people figured out that there was a
way to do it, everybody came up with their own methods and
some just aren't compatible with others.
RCOMM is a combination of all of the best TSR methodology
available today. Release 1 was reliable under most circum-
stances and release 2 is nearly airtight. But just the same
one of you is going to fire up Turbo-this along with that-Calc
along with RCOMM along with.......and the PC will lock up.
If this happens to you, there is some debugging you can do on
your own. What you have to is try different combinations of TSR's
and/or different foreground applications and TSR's. If you can
come up with a situation where you can say "I do this and the
system locks up" every time. Then you have isolated the problem.
Once you have it isolated the solution is up to you. Either don't
run the offending program or clear all other TSR's when you need
to run the offender. It's like the old joke about the guy who
goes to see his doctor and says "Doc every time I do this, it
hurts" and the doctor says "well don't do it then".
But seriously folks, if you find a case where RCOMM is
incompatible with something, drop me a line and let me know.
Once again the address is:
Thomas Duller
P.O. Box 27095
Milwaukee, WI. 53227
Be as specific as you can. This leads us to the question
of support. Please read on.
RCOMM - Resident Communications. Version 2.0 Page 13
Copyright (C) 1988 by Thomas Duller. All rights reserved.
RCOMM support policy.
With release 1, there really wasn't any specific support policy.
I just said "let me know what you think". This worked out pretty
well in most cases because release 1 was more of a "trial
balloon" than anything. The contribution rate was horrible, well
actually none at all, but I did hear from a lot of nice people
from all over with a lot of good ideas and a lot of nasty bugs
to be fixed. I'd like to thank everybody now. Thank you. You know
who you are.
OK the bugs have all been fixed and most of the new ideas have
been implemented. So now it's time to come up with a formal policy.
It's not that I don't want to be bothered any more. Quite the
contrary, some of my best ideas have come from people I don't
even know. However, a lot of people have been getting my home
phone number from directory assistance and calling me! Please
don't do that. That's why I got the P.O. box. Write to me. I'd
love to hear from you and I'll write you back. Promise.
So anyway here's the support policy:
If you have any problems write me at:
Thomas Duller
P.O. Box 27095
Milwaukee, WI. 53227
That's it. What do you want for $25.00? 24 hour on site support?
Contributors will, of course, receive priority.
RCOMM - Resident Communications. Version 2.0 Page 13
Copyright (C) 1988 by Thomas Duller. All rights reserved.
Using RCOMM in conjunction with your current comm program.
If you really like your current modem program and just want the
added capability of background file transfers, RCOMM can do
that too. All you have to do is load RCOMM before your modem
program, then load your modem program.
Using your modem program, make your connection and take care of
your terminal business. When you are ready to up/download, pop
RCOMM up over your modem program and start the up/download using
RCOMM. Once the file transfer has started, exit RCOMM using the
<Alt>-X function. Now you will be back in your own modem program.
Exit your modem program WITHOUT DROPPING CARRIER and RCOMM will
do the file transfer in the background. If you can't exit your
modem program without dropping carrier (as I am afraid is often
the case), you can "shell out of it" if it has that capability.
If you can't do that then I guess you have a choice to make.
If your modem program is really fussy about keeping it's com
interrupt you may need to exit your modem program before pop-
ping RCOMM up to start the file transfer. Play around with it.
It should work one way or the other. Since there are so many
modem programs around and since I am completely satisfied with
RCOMM's terminal functions I have no intention of coming up with
specific instructions for specific programs. If enough people
request it, I might be convinced to come up with just a back-
ground file transfer module similar to the DSZ modules. If
those requests are accompanied by contributions that would be
very convincing.
Well, that's about it. I'd just like to add a personal note here
(for those of you who bothered to read this far). RCOMM got it's
start as a simple program for my own use. It seemed to take on a
life of it's own and made me work on it until it seemed like it
was something people would be interested in. That was release 1.
Even though I didn't make a single cent on it, I had enough input
from enough nice people to keep on and come up with this release.
You see, RCOMM is a shareware product in the truest sense of the
word. You see, this isn't some software company. I'm just a guy
with an idea. I'm sitting here in my living room (downloading
some files in the background) and writing this documentation. As
is the case with all good things, too much is too much. At the
moment I am sick of RCOMM. If there is ever to be a release 3, it
is up to you. I need your support. Kind words are nice, but cash
is even better. I don't expect to get rich off of this deal but
it would be nice to get something out of it. Your move..........